IRIX Base Documentation 2002 November

home *** CD-ROM | disk | FTP | other *** search

/ IRIX Base Documentation 2002 November / SGI IRIX Base Documentation 2002 November.iso / usr / relnotes / eoe / ch5.z / ch5

Wrap

Text File | 2002-10-08 | 15.0 KB | 397 lines

- 1 - 5. _K_n_o_w_n__P_r_o_b_l_e_m_s__a_n_d__W_o_r_k_a_r_o_u_n_d_s This chapter discusses known problems in IRIX 6.5 and ways to work around them. +o Programs built o32 running on desktop platforms released since Irix 6.2 (O2 and OCTANEs) and with default system configuration, may be returned values of 0x80000000 for resource limits RLIMIT_DATA and RLIMIT_VMEM from a call to getlimit(). However, setrlimit() will reject this value as invalid. o32 programs do not suffer from this problem on any other platform. n32 programs are not affected by this problem. The workaround is to use systune to reduce the associated default values. This problem affects systems with CPU types IP26, IP28, IP30, or IP32. +o The Qlogic SCSI controller is not capable of operating at synchronous speeds of 300ns or more per cycle. If you have a slow scsi device that is capable of synchronous negotiations but at 300 ns period or greater you must disable synchronous negotiations for that device. You can disable sync for the whole bus by using the DEVICE_ADMIN directive in /var/sysgen/system/irix.sm. For example, to disable sync on the external SCSI bus on an OCTANE system, add the following line to irix.sm and then run autoconfig(1M) and reboot the system: DEVICE_ADMIN: /hw/node/xtalk/15/pci/1/scsi_ctlr/0 ql_sync_enable=0 +o The XFS Guaranteed Rate I/O (GRIO) feature contained in eoe.sw.xfsrt can be used to access "real-time" files. The GRIO API has undergone changes since IRIX 6.2, and are described in the grio(1M), grio_bandwidth(1M), grio(5), grio_disks(4) and associated man pages. +o Deleting ip aliases can cause kernel panics. The workaround is not to delete them. +o The system automatically mounts a pseudo-filesystem called /_h_w. This file system should never be unmounted (i.e. _u_m_o_u_n_t -_a should be used with caution). The command /_e_t_c/_m_n_t_h_w_g_f_s can be used to remount /_h_w if necessary. See _h_w_g_f_s(4) for more information. - 2 - +o Use of file-locking operations on fifos can cause a panic. +o fsr (the EFS filesystem reoganizer) will get into an infinite loop when it encounters an EFS filesystem on an XLV volume. You can avoid the problem by removing the rw option from the fstab entry for the affected filesystem(s), see the fsr(1M) manual page. This disables fsr for the filesystem. +o OCTANE and Origin/Onyx2 systems have IBM(R) PC/AT(tm)- like DB-9 male serial port connectors. Some existing serial devices, such as Dial and Button boxes, have male DB-9 serial connectors. These connectors are designed for the DB-9 female serial port connectors found on the CHALLENGE and Onyx systems. The difference is not merely in the gender of the connectors; the pinout is different, and a conversion cable is required to connect devices with the older connectors to the newer systems. See the serial(7) man page for the pinouts of the CHALLENGE/Onyx and OCTANE/Origin/Onyx2 connectors, which can be used to create a conversion cable. Recently shipped versions of some devices (including Dial and Button boxes) may have PC/AT(tm)-like DB-9 female serial port connectors that will connect directly to OCTANE and Origin/Onyx2 systems. +o OCTANE Duo systems will need check to make sure the appropriate Xservers file is on the system. Use "versions changed" (see versions(1M)) to check for the previous version of Xservers (will be Xservers.O). Compare the Xservers.O with the new Xservers.2key to check for any changes or additions. Without the appropriate Xservers file the second head on the OCTANE Duo system will not be activated. Please see your OCTANE Duo Installation Guide for additional details. +o On Onyx2, Origin2000, and OCTANE systems with Reality, InfinteReality, InfiniteReality2, SI, SSI, or MXI graphics, real-time determinism breaks when the X server is terminated. Avoid terminating the X server when real-time determinism is required. If the X server must be terminated while real-time deteminism is required, a workaround for Onyx2 and Origin2000 systems with Reality and InfiniteReality, and InfiniteReality2 graphics can be used. Set the non-volitile RAM's console variable to "d," directing console output out the console serial port instead of - 3 - the graphics display. No workaround exists for OCTANE systems and Origin2000 systems with SI, SSI, or MXI graphics. +o The IRIX 6.5.6 feature stream supports the STP protocol over GSN. The /etc/protocols file contains a new entry for STP, however, if the protocols table is obtained from a remote NIS server, it is important to ensure that this NIS table contain a similar entry for STP, otherwise tools such as netstat will not give output for STP. +o iwsh: Backspacing does not erase all Shift-JIS characters (Bug #579964). The double width characters in EUC locale require two backspace to remove one double-width Japanese character. However when Japanese Shift-JIS characters are to be removed by backspacing, for example in a command line, some characters may still be left displayed on the terminal even though all characters were actually removed in the line buffer. This behavior depends on the character being backspaced. In some situation, all characters will be removed, while in other cases a part of character string will be left. In extreme case, none of the characters will be erased, even though they were actually removed from the line buffer. A workaround is to use vi or emacs shell editing mode. +o iwsh, kterm: Inability to cut-and-paste or input a certain Shift-JIS characters in Shift-JIS environment (Bug #567031, #579362) With terminal emulators such as iwsh and kterm running in a Shift-JIS environment (ja_JP.SJIS), keyboard input or cut-and-paste operation involving certain Shift-JIS characters results in that particular character being incorrectly processed by the _t_t_y driver. A workaround is not to strip input characters to seven bits for the terminal emulator (i.e. stty -istrip) for Shift_JIS locale. If you are using sh or ksh, it is suggested that the following statements be included in ._p_r_o_f_i_l_e. CTYP=`locale -c charmap | tail -1` if [ $CTYP = "sjis" ] then stty -istrip fi - 4 - +o Desktop: Desktop does not recognize multibyte text files as such (Bug #588620) The Inidigo Magic Desktop (IMD) and associted tools (such as the filemanager) do not recognize files containing multibyte character as text files. Rather, they will recognize them as binary data files and as a result the default text editor will not be started when the user tries to open such file. There is no known workaround. +o CATIA: Roman Numeral Inputs for CATIA Application In CATIA application, the Roman numerals can be entered in a multi-byte character set (MBCS) text filed and will be displayed correctly in the CATIA's drawing area. However, they are not displayed correctly in an active text field. As an example, the sequence of steps for inputting a Roman numeral character in CATIA is given below: +o In a text input field set to MBCS mode, input the Shift-JIS code of a Roman numeral. +o The input method's pre-edit area will not show the character. +o After confirming the pre-edit, the specified Roman numeral does not appear correctly in the active text field in MBCS mode but will be displayed by two unrelated characters. However, the codepoint is valid and the data correctly represents the Roman numeral character. +o After leaving the active text field, the Roman numeral character will be displayed correctly. +o Finally, the Roman numeral character will be displayed correctly in CATIA's drawing area. This anomaly exists in CATIA's text objects such as comment, TEXT, and TEXTD2. +o Irix 6.5.3 and 6.5.4 NFSv2 clients will sometimes report incorrect directory sizes. Workarounds are to use NFSv3 or the noac mount option on the NFSv2 client. +o XXXXVVVVMMMM: Volume Manager for CXFS +o XVM can be used only when running CXFS. XVM is the new volume manager that is required when you use the CXFS filesystem. XVM can be used only when - 5 - it is layered with the CXFS filesystem. XVM is not currently supported as a standalone volume manager to replace XLV. If CXFS is not being used on a system, SGI will support only XLV as a standalone volume manager. The current required licensing for CXFS includes the use of XVM with CXFS. +o Do not label your boot disk as an XVM disk. While the XVM user command tool (i.e., /sbin/xvm) will permit users to label their boot disk as an XVM disk, this feature is not yet supported by XVM. There are two risks associated with labeling your boot disk as an XVM disk: +o The possible corruption of your root file system. +o You will not be able to do anything in the miniroot, including installing software or recovering your system disk. The miniroot will complain that it cannot mount the root file system. +o XVM is qualified only on IP27 (Origin 200/2000, and Onyx2) and IP30 (Octane). +o Use the xvm give, steal commands with extreme caution. xvm runs either in the local domain or in the cluster domain, and XVM disks are classified according to whether they are owned by the local domain, an active cluster domain, or a foreign domain. The xvm give and steal commands permit the administrator to change the ownership of a list of XVM disks. Cautionary notes: +o The give command is always a safer option than the steal command, for changing domain ownership of XVM disks. The steal command is intended to be used as a last resort, and only when the give command cannot be used. +o In general, an xvm probe command be run following the give command. In the case that the XVM disk was given to a local host, the probe command is run on that new owner host. In the case that the XVM disk was given to a new cluster, the probe command is run on any host that is a member of that cluster. - 6 - +o The give/steal command should never be used so that a multi-disk volume configuration ends up being split between domains. The user must ensure that the list of disks to move from one domain to another, is complete, in the sense that all volume configurations are fully contained on this set of disks. The xvm show command can be used to examine the top-down configuration for all volumes in the system, including the full set of disks which contain pieces of these volumes. +o IRIX 6.5.8 contains security fixes to the fam daemon and libfam.a client library; FAM clients are now treated as untrusted until they authenticate themselves. Earlier versions of the libfam.a client library do not perform authentication, so existing clients may not receive FAM events for some files. The fam daemon has a backwards compatibility mode which can be used to disable authentication so that existing clients will continue to work, but by default, this mode is unused. To help diagnose problems caused by authentication disagreements between fam and its clients, a message is put in the syslog the first time each unauthenticated client has a request denied because of insufficient permissions. The message describes the problem and refers to the fam(1M) man page, which contains more information and instructions. +o For IRIX 6.5.17, a fix was implemented to ensure that sadc/sar will give a correct vswap value. To enable the fix, reboot the system to the new kernel. If a reboot is not peformed after the upgrade, sadc/sar will continue to operate, but the vswap values may be inaccurate. If the accuracy of the sadc/sar number are important, it is recommended that you reboot as soon as possible.